<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <title>Welcom to vim – Practice Document</title>
  <meta name="description" content="A long HTML file for Vim search and replace practice." />
  <style>
    body { font-family: system-ui, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif; line-height: 1.6; }
    code, pre { font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, "Liberation Mono", monospace; }
  </style>
</head>
<body>
  <!-- Purpose: Provide many repeatable typos and patterns for Vim /, :s, and :%s practice. -->
  <header>
    <h1>Welcom to Vim</h1>
    <p class="lead">Vim is a txt editr. It is powrful and fast. This page is for practis with search, replace, and navgation.</p>
    <nav>
      <ul>
        <li><a href="#intro">Into</a></li>
        <li><a href="#install">Instalation</a></li>
        <li><a href="#motions">Motons</a></li>
        <li><a href="#editing">Edting</a></li>
        <li><a href="#search">Serach & Replce</a></li>
        <li><a href="#macros">Macors</a></li>
        <li><a href="#faq">FAQ</a></li>
      </ul>
    </nav>
  </header>

  <main>
    <section id="intro">
      <h2>Into: Why Vim?</h2>
      <p>Vim (sometimes written as VIM or vim) is a text editr designed for efficency. Many people consider it powrful because it lets you keep your hands on teh keyboard.</p>
      <p>In this doc, you will fix commen typos: Welcom → Welcome, editr → editor, powrful → powerful, practis → practice, navgation → navigation, Into → Intro, Instalation → Installation, Motons → Motions, Edting → Editing, Serach → Search, Replce → Replace, Macors → Macros, efficency → efficiency, teh → the, commen → common.</p>
      <p>Also normalize casing: change VIM and vim to Vim (but not inside code examples).</p>
      <p>[FIXME] Some lines include extra    spaces at the end.   
      Another line ends with spaces too.    
      Make sure to remove trailing spaces.   </p>
    </section>

    <section id="install">
      <h2>Instalation</h2>
      <p>On Linux you can install vim with your package manager. On macOS use Homebrew to get VIM. On Windows, download the installer. Many guides say "Welcom to VIM" when you first open it.</p>
      <ul>
        <li>Linux: <code>sudo apt-get instal vim</code> (typo intentional)</li>
        <li>macOS: <code>brew instal vim</code> (typo intentional)</li>
        <li>Windows: Use the GUI installer and check the box that says "Add VIM to PATH".</li>
      </ul>
      <p>Remember: in this secton, replace all occurrences of VIM and vim with Vim, but do not change the case in code blocks.</p>
    </section>

    <section id="motions">
      <h2>Motons</h2>
      <p>Basic motons include <code>w</code>, <code>b</code>, and <code>e</code> to move by words. Use <code>gg</code> to jump to the start and <code>G</code> to jump to the end.</p>
      <p>Try fast navgation: search for "Welcom" with <code>/Welcom</code> and press <code>n</code> / <code>N</code> to jump between matches.</p>
      <p>There are also line motions like <code>0</code>, <code>^</code>, and <code>$</code>. Use counts: <code>5w</code> moves five words. This is very powrful once you learn it.</p>
      <p>Sometimes we repeat the same typo to make global replace meaningful: powrful, powrful, powrful!</p>
    </section>

    <section id="editing">
      <h2>Edting</h2>
      <p>Use <code>x</code> to delete a charracter, <code>r</code> to replace one charracter, and <code>a</code>/<code>i</code> to enter insert mode. Undo with <code>u</code>, redo with <code>Ctrl-r</code>. These are the basics of a text editr.</p>
      <p>Here are deliberate misspellings and patterns:</p>
      <ul>
        <li>editr, editr, editr (should become editor)</li>
        <li>teh → the (appears many times: teh, teh, teh)</li>
        <li>practis → practice</li>
        <li>efficency → efficiency</li>
        <li>navgation → navigation</li>
        <li>Into → Intro</li>
        <li>Edting → Editing</li>
      </ul>
      <p class="note">This paragraph has trailing spaces on purpose.   </p>
      <p class="note">This paragraph also has trailing spaces.    </p>
      <p class="note">Remove all trailing spaces in the whole document.     </p>
    </section>

    <section id="search">
      <h2>Serach & Replce</h2>
      <p>Use <code>:s/old/new/</code> to replace the first match in a line, and <code>:%s/old/new/g</code> to replace in the whole file. Practice with commen typos: Welcom, editr, powrful, practis, navgation, Serach, Replce.</p>
      <p>Example incorrect lines for batch operations:</p>
      <pre><code>// Javascript sample with intentional mistakes
function greet(){
  console.log('Welcom to vim!'); // do not change case inside strings for now
}
// find and fix: Javasript → JavaScript, vim → Vim in prose, but NOT here in code
</code></pre>
      <p>List of repeated typos for global replacement:</p>
      <ul>
        <li>Welcom Welcom Welcom</li>
        <li>editr editr editr</li>
        <li>powrful powrful powrful</li>
        <li>practis practis practis</li>
        <li>navgation navgation navgation</li>
        <li>Serach Serach Serach</li>
        <li>Replce Replce Replce</li>
      </ul>
      <p>Some lines include mixed case: VIM, vim, and Vim. Normalize to Vim in prose.</p>
    </section>

    <section id="macros">
      <h2>Macors</h2>
      <p>Though not required, you may record a macro (qa … q) to fix repeated patterns. For instance, correct charracter-level issues across many lines. But focus on / search and :s replace first.</p>
      <p>Below are 20 repetitive paragraphs with scattered typos to encourage :%s usage:</p>
      <ol>
        <li>Paragraph 01: Vim is powrful because it makes teh editor fast. Many users say Welcom to Vim again and again.</li>
        <li>Paragraph 02: This editr allows practis with motions and navgation.</li>
        <li>Paragraph 03: Into the world of efficency, vim shines as a txt editr.</li>
        <li>Paragraph 04: Serach and Replce are commen in daily edting.</li>
        <li>Paragraph 05: Some write VIM or vim, but the guide prefers Vim in normal text.</li>
        <li>Paragraph 06: Charracter fixes with x and r are powrful when used with counts.</li>
        <li>Paragraph 07: Trailing spaces should be removed at teh end of lines.   </li>
        <li>Paragraph 08: Welcom Welcom Welcom — a good candidate for :%s.</li>
        <li>Paragraph 09: The edting workflow improves with practis and patience.</li>
        <li>Paragraph 10: Use gg and G for quick navgation across teh file.</li>
        <li>Paragraph 11: The editr supports multiple undo levels, which is powrful.</li>
        <li>Paragraph 12: Fix Javasript spelling only in prose, not inside code blocks.</li>
        <li>Paragraph 13: Replace Serach with Search and Replce with Replace.</li>
        <li>Paragraph 14: Correct Into → Intro at the top mennu.</li>
        <li>Paragraph 15: Instalation steps often say "Welcom to VIM" first.</li>
        <li>Paragraph 16: Remove extra    spaces inside lines where needed.</li>
        <li>Paragraph 17: edtir edtir edtir — a more broken variant to turn into editor.</li>
        <li>Paragraph 18: efficency and navgation both need fixes.</li>
        <li>Paragraph 19: practis makes perfect; edting gets faster over time.</li>
        <li>Paragraph 20: Finish with a :%s to normalize Vim casing outside code.</li>
      </ol>
    </section>

    <section id="faq">
      <h2>FAQ</h2>
      <details>
        <summary>How to save and quit?</summary>
        <p>Type <code>:wq</code>. If stuck, press <code>Esc</code> to return to normal mode. Many beginners type <code>:q!</code> to force quit, but make sure you saved changes.</p>
      </details>
      <details>
        <summary>How to jump to top or bottom?</summary>
        <p>Use <code>gg</code> to go to the first line and <code>G</code> to go to the last line.</p>
      </details>
      <details>
        <summary>How to search?</summary>
        <p>Use <code>/pattern</code> then <code>n</code> or <code>N</code> to navigate. For replace, try <code>:%s/old/new/g</code>.</p>
      </details>
      <p class="foot">Thank you and Welcom to Vim!   </p>
    </section>
  </main>

  <footer>
    <p>© 2025 Vim practis page. Some words intentionally misspelled for edting training.</p>
  </footer>
</body>
</html>
